-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implement env variable expansion for kaniko builds #3974
implement env variable expansion for kaniko builds #3974
Conversation
Codecov Report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs more explanation
310d5a6
to
2c532db
Compare
…not set explicitly). resolves GoogleContainerTools#3229
2c532db
to
a199ac8
Compare
@tejal29 I think the CI re-build is stuck |
@DanielSel It seems that Travis is stuck. You can push an empty commit to force it to trigger another job. That worked for me once before. |
@DanielSel you need to run |
Hey guys, |
@DanielSel np, I'll close the PR for now. Please reopen once you've made the change. |
I made the change and re-submitted the PR here: #4557 |
if err != nil { | ||
t.Fatalf("error processing generated env variables from image uri: %s", err) | ||
} | ||
env, err := evaluateEnv(artifact.Env, generatedEnvs...) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The documentation in v2beta3.json
states that the env vars are available for buildArgs:
but it seems that is it only the case for env:
. @DanielSel Should I report a bug?
Adds environment variable expansion for kaniko builds (to address currently inconsistent behaviour between buildArgs and envs).